Update logging for containerization - #5095
Draft
jsvarova wants to merge 19 commits into
Draft
Conversation
jsvarova
marked this pull request as draft
July 22, 2026 21:29
|
The PR preview for 78211fa is available at theforeman-foreman-documentation-preview-pr-5095.surge.sh The following output files are affected by this PR: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes are you introducing?
Adding a chapter on containerized logging.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Containerized Satellite 6.20 replaces the traditional file-based logging model with a journald-centric architecture. This is a breaking change: log file paths that administrators have relied on for years (/var/log/foreman, /var/log/candlepin, /var/log/httpd) no longer exist in containerized deployments. Without updated documentation, administrators cannot view service logs, configure log levels for troubleshooting, collect diagnostic data for support cases, or manage log retention to prevent disk exhaustion. The parent epic SAT-43762 (priority: Blocker) explicitly requires that administrators can perform all of these tasks. Every existing script, monitoring integration, and mental model built around traditional log paths must be updated.
Contributor checklists